chore(main): release helm-slim-spire 1.4.1 - #1905
Conversation
f4fa67c to
b59ee46
Compare
|
Warning Review limit reached
Next review available in: 46 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe slim-spire chart version changed from 1.4.0 to 1.4.1. The release manifest matches the new version. The changelog records the release and the SPIRE upgrade to 1.15.2. Changesslim-spire release update
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
b59ee46 to
4a6d1db
Compare
Signed-off-by: Agntcy Build Bot <build@agntcy.io>
4a6d1db to
4bdd6eb
Compare
🤖 I have created a release beep boop
1.4.1 (2026-08-05)
Bug Fixes
This PR was generated with Release Please. See documentation.